Method and system for identifying conflicts in a roof truss to roof truss horizontal interface

ABSTRACT

The present invention is a method for accessing a model, wherein the model incorporates a plurality of roof truss assemblies, wherein the assemblies are comprised of a plurality of members; detecting at least one interface between at least two roof truss assemblies, and wherein the interface type is detected; recording, by at least one processors, a interface type, wherein a set of required values based on the interface type are identified; calculating a set of actual values associated with the interface; comparing if the set of actual values is within the required values; identifying a modification to at least one roof truss assembly involved in the interface; incorporating the modification into the model; and analyzing the model for newly created interfaces between a set of members of the model.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part (and claims the benefit of priority under 35 USC 120) of U.S. Pat. No. 1,113,310 issues on Sep. 7, 2021. The disclosure of the U.S. Pat. No. 1,113,310 is considered part of (and is incorporated by reference in) the disclosure of this application.

BACKGROUND

This disclosure relates generally to building construction and in particular, to the method, computer program, or computer system for providing the quality control of the material for the building construction and determining conflicts within the building construction.

A typical building or structure is comprised of having different components like foundation, walls, joists, trusses, sheathings, and many other components. When these components are connect with each other in a proper form, the structure or building is constructed correctly. Each individual component is used to form a larger assembly or panel. If each component is not with the correct specification or dimensions then it leads to conflicts in the assembly process. This results in lost of time, wasted material, and an increase in cost. For example, when constructing roof trusses, conflicts between the members of the panel can occur in overlapping of the members, wrong placing of dimples locations, insufficient overlap length, and overlap width. Checking each individual member and panel is very time consuming and critical task for the engineer.

During the building construction, the connections and placing of each roof trusses is important for a hassle and conflict free construction. The roof trusses relative to the other roof trusses assists in creating a building that is properly constructed. The assembly of the roof is important to avoid any issues with the building down the road and to keep the occupants safe from the elements. Traditional method of reviewing the constructability checks for each individual roof truss member panel manually in the detailing software is time consuming and chances of error are more.

Therefore, it is beneficial to assist each of the roof truss to roof truss horizontal and vertical interfaces at the earliest stage to determine where issues exist and preemptively correcting these issues before construction begins.

SUMMARY

In a first embodiment the present invention is a method accessing a model, wherein the model incorporates a plurality of roof truss assemblies, wherein the assemblies are comprised of a plurality of members; detecting at least one interface between at least two roof truss assemblies, and wherein the interface type is detected; recording, by at least one processors, a interface type, wherein a set of required values based on the interface type are identified; calculating a set of actual values associated with the interface; comparing if the set of actual values is within the required values; identifying a modification to at least one roof truss assembly involved in the interface; incorporating the modification into the model; and analyzing the model for newly created interfaces between a set of members of the model.

In a second embodiment the present invention is a program product accessing a model, wherein the model incorporates a plurality of roof truss assemblies, wherein the assemblies are comprised of a plurality of members; detecting at least one interface between at least two roof truss assemblies, and wherein the interface type is detected; recording, by at least one processors, a interface type, wherein a set of required values based on the interface type are identified; calculating a set of actual values associated with the interface; comparing if the set of actual values is within the required values; identifying a modification to at least one roof truss assembly involved in the interface; incorporating the modification into the model; and analyzing the model for newly created interfaces between a set of members of the model.

In a third embodiment the present invention is a system accessing a model, wherein the model incorporates a plurality of roof truss assemblies, wherein the assemblies are comprised of a plurality of members; detecting at least one interface between at least two roof truss assemblies, and wherein the interface type is detected; recording, by at least one processors, a interface type, wherein a set of required values based on the interface type are identified; calculating a set of actual values associated with the interface; comparing if the set of actual values is within the required values; identifying a modification to at least one roof truss assembly involved in the interface; incorporating the modification into the model; and analyzing the model for newly created interfaces between a set of members of the model.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a block diagram depicting a computing environment, in accordance with one embodiment of the present invention.

FIG. 2 depicts a block diagram depicting the internal and external components of the server and computing device of FIG. 1 , in accordance with one embodiment of the present.

FIG. 3 depicts a cloud computing environment, in accordance with one embodiment of the present invention.

FIG. 4 depicts a flowchart of the operational steps of a method for determining the directional conflict checks for roof trusses or members in building within the computing environment of FIG. 1 , in accordance with one embodiment of the present invention.

FIG. 5 depicts an architectural illustration of a front view of a structure, in accordance with one embodiment of the present invention.

FIG. 6 depicts an architectural illustration of a profile view of a structure, in accordance with one embodiment of the present invention.

FIG. 7 depict an architectural illustration of a finished floor layout for a structure, in accordance with one embodiment of the present invention.

FIG. 8 depicts a model of a frame of a structure, in accordance with one embodiment of the present invention.

FIG. 9 depicts a model of a roof truss system showing the connection in a horizontal plane, in accordance with one embodiment of the present invention.

FIG. 10 depicts a model of a roof truss system showing the connection in a horizontal plane, in accordance with one embodiment of the present invention.

FIG. 11 depicts a model of a roof truss system showing the connection in a vertical interface, in accordance with one embodiment of the present invention.

FIG. 12 depicts a model of a roof truss system showing the connection in a vertical interface, in accordance with one embodiment of the present invention.

FIG. 13 depicts a model of a roof truss and the vertical interface between the roof truss and the roof assembly, in accordance with one embodiment of the present invention.

DETAILED DESCRIPTION

The present invention generally relates to the process of analyzing a building to identify conflicts or design errors, and correcting the errors at the design stage so the construction can be completed with minimal or no issues. Through the location of the roof trusses and the interaction between the roof truss interfaces to determine if they have the correct properties and if they are outside of the tolerance values, correcting the errors with the roof trusses.

The present invention uses the unique feature of analyzing the roof trusses and the interaction between the roof trusses in the horizontal and vertical interfaces and determining if there are any inter-assembly conflicts. This includes the vertical interfaces between the trusses, the horizontal interfaces between the trusses, and the interface between the structural trusses and the non-structural truss system. In instances where conflicts are identified the roof truss member(s) and/or assemblies are added to a sick list, which identifies the type of conflict. The unique feature saves the time of review the building manually and eliminate the chance of error with the construction process.

In the typical construction process a model of the building (e.g. structure, home, office building, hospital, garage, barn, apartment building, etc.) is created. This model is comprised of all the members which form the frame of the building. The members form assemblies (e.g. wall panels, joists, trusses, etc.) which them form the walls, floors, and roof. The next step is to generate the manufacturing files for the roll forming machine to produce these members to the design specifications. However, the generation of these manufacturing files is not advised or able to be completed until a verification of possible conflicts of the systems is completed.

Otherwise the potential for cold formed steel studs to be manufactured without the proper measurements, cutouts or designs elements. This will require the remanufacturing of the members, or manual modification of the parts need to be completed on the job site. Both of these take time and additional resources to complete. The reviewing of the model from constructability aspect and identify the possible conflicts is a time consuming task before the roof truss members are manufactured. If the user is able to quickly identify the conflicts in the model, the entire process of constructing the building can be shortened.

The reviewing of the 3D model from constructability aspect and identify the possible conflicts in the walls is one of the major time consuming task. If the user is able to quickly check and identify the possible conflicts, they can increase the speed of manufacturing, and having a program that highlights these conflicts only further increases the speed at which the project can be completed.

The present invention provides for an advantage of allowing the review of the drawings or models by providing a unique process of identifying internal and external conflicts with the roof truss members. The individual members of the roof truss which are conflicting are identified and marked for the reviewer to easily identify and correct the conflicts. The conflicts can be identified during the process of building detailing by using the present inventions conflict check method and system.

The term “conflict” is used for any incidence which results in the member or the interaction between members to be outside of a predetermined tolerance of acceptable values. This can be based on state, federal or local building codes, manufacturing machine limitations, or inconsistencies or inaccuracies with the model or drawings. For example, if a member is not at the required position, not within the required specifications, not adhering to predetermined codes, or the like a conflict may be present. Required position means the Global position of the member in reference to the modeling software x, y, and z, axes. In another embodiment, the properties of the member may be impossible to manufacture based on the cold formed steel construction tolling operation limitations

The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firejoists, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowcharts and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowcharts may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

It is understood in advance that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, embodiments of the present invention are capable of being implemented in conjunction with any other type of computing environment now known or later developed.

Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g. networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.

Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.

Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based e-mail). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firejoists).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).

A cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure comprising a network of interconnected nodes.

FIG. 1 depicts a block diagram of a computing environment 100 in accordance with one embodiment of the present invention. FIG. 1 provides an illustration of one embodiment and does not imply any limitations regarding the environment in which different embodiments may be implemented.

In the depicted embodiment, computing environment 100 includes network 102, computing device 104, and server 106. Computing environment 100 may include additional servers, computers, or other devices not shown.

Network 102 may be a local area network (LAN), a wide area network (WAN) such as the Internet, any combination thereof, or any combination of connections and protocols that can support communications between computing device 104 and server 106 in accordance with embodiments of the invention. Network 102 may include wired, wireless, or fiber optic connections.

Computing device 104 may be a management server, a web server, or any other electronic device or computing system capable of processing program instructions and receiving and sending data. In other embodiments, computing device 104 may be a laptop computer, tablet computer, netbook computer, personal computer (PC), a desktop computer, or any programmable electronic device capable of communicating with patient computing device 104 via network 102. In other embodiments, computing device 104 may be a server computing system utilizing multiple computers as a server system, such as in a cloud computing environment. In one embodiment, computing device 104 represents a computing system utilizing clustered computers and components to act as a single pool of seamless resources. Computing device 104 may include components, as depicted and described in further detail with respect to FIG. 1 .

Server 106 may be a management server, a web server, or any other electronic device or computing system capable of processing program instructions and receiving and sending data. In other embodiments server 106 may be a laptop computer, tablet computer, notbook computer, personal computer (PC), a desktop computer, or any programmable electronic device capable of communicating via network 102. In one embodiment, server 106 may be a server computing system utilizing multiple computers as a server system, such as in a cloud computing environment. In one embodiment, server 106 represents a computing system utilizing clustered computers and components to act as a single pool of seamless resources. In the depicted embodiment conflict identification program 108 and database 110 are located on server 106. Server 106 may include components, as depicted and described in further detail with respect to FIG. 1 .

Conflict Identification program 108 has the unique feature of constructability conflict check in which the roof truss system and assemblies are analyzed to determine if a roof truss has a conflict with another roof truss which interfaces with one another. The roof trusses which are conflicting with each other are added to a sick list which identifies all of the conflicting roof trusses. The conflict can be between any material, component, member or the roof trusses which interface with another roof truss which either interfere with one another or are not within the proper code requirements. The sick list shows the condition under which the member is conflicting in constructability conflict check, so personnel can easily make the necessary modifications to correct the conflicts and produce a model of the building without any conflicts.

In the depicted embodiment, Conflict identification program 108 utilizes network 102 to access the computing device 104 and to communicate with database 110. In one embodiment, Conflict identification program 108 resides on computing device 104. In other embodiments, Conflict identification program 108 may be located on another server or computing device, provided Conflict identification program 108 has access to database 110.

Database 110 may be a repository that may be written to and/or read by Conflict identification program 108. Information gathered from computing device 104 and the 1-dimensional, 2-dimensional, and 3-dimensional drawings and models as well as the requirements so that the materials and members are identified as conflicting or non-conflicting. In one embodiment, database 110 is a database management system (DBMS) used to allow the definition, creation, querying, update, and administration of a database(s). In the depicted embodiment, database 110 resides on computing device 104. In other embodiments, database 110 resides on another server, or another computing device, provided that database 110 is accessible to Conflict identification program 108.

FIG. 2 , a schematic of an example of a cloud computing node is shown. Cloud computing node 10 is only one example of a suitable cloud computing node and is not intended to suggest any limitation as to the scope of use or functionality of embodiments of the invention described herein. Regardless, cloud computing node 10 is capable of being implemented and/or performing any of the functionality set forth hereinabove.

In cloud computing node 10 there is a computer system/server 12, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 12 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context of computer system executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 12 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.

FIG. 2 , computer system/server 12 in cloud computing node 10 is shown in the form of a general-purpose computing device. The components of computer system/server 12 may include, but are not limited to, one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including system memory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 12, and it includes both volatile and non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and/or cache memory 32. Computer system/server 12 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 34 can be provided for reading from and writing to a non removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 18 by one or more data media interfaces. As will be further depicted and described below, memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42, may be stored in memory 28 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 42 generally carry out the functions and/or methodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more external devices 14 such as a keyboard, a pointing device, a display 24, etc.; one or more devices that enable a user to interact with computer system/server 12; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 12 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 22. Still yet, computer system/server 12 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 20. As depicted, network adapter 20 communicates with the other components of computer system/server 12 via bus 18. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 12. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, and external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

FIG. 3 , illustrative cloud computing environment 50 is depicted. As shown, cloud computing environment 50 comprises one or more cloud computing nodes 10 with which local computing devices used by cloud consumers, such as, for example, personal digital assistant (PDA) or cellular telephone 54A, desktop computer 54B, laptop computer 54C may communicate. Nodes 10 may communicate with one another. They may be grouped (not shown) physically or virtually, in one or more networks, such as Private, Community, Public, or Hybrid clouds as described hereinabove, or a combination thereof. This allows cloud computing environment 50 to offer infrastructure, platforms and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device. It is understood that the types of computing devices 54A-C shown in FIG. 2 are intended to be illustrative only and that computing nodes 10 and cloud computing environment 50 can communicate with any type of computerized device over any type of network and/or network addressable connection (e.g., using a web browser).

Referring back to FIG. 2 , the Program/utility 40 may include one or more program modules 42 that generally carry out the functions and/or methodologies of embodiments of the invention as described herein. Specifically, the program modules 42 may analyze a building model, locate the roof trusses determine the interaction between the trusses, determine if a conflict exists, and identify the member(s) involved in the conflict and provide a potential solution to the conflict. Other functionalities of the program modules 42 are described further herein such that the program modules 42 are not limited to the functions described above. Moreover, it is noted that some of the modules 42 can be implemented within the infrastructure shown in FIGS. 1-3 .

FIG. 4 depicts flowchart 400 depicting a method according to the present invention. The method(s) and associated process(es) are now discussed, over the course of the following paragraphs, in accordance with one embodiment of the present invention.

In step 402, the conflict identification program 108 analyzes the model to identify the roof truss members. Based on the received model or image type, the conflict identification program 108 extracts the roof truss members from the other members and systems. In some embodiments where the model has all the members individually generated, the conflict program 108 is able to easily extract the roof truss members. Either from identifying the members first or identifying the roof truss assembly and then identifying the members within the roof truss. In instances where the model does not have each individual member created, the conflict identification program 108 analyzes the model or images to first determine which surfaces are roofs versus floors or walls. This analysis is based on the data extracted from the model that identifies the measurements of the roof based on the measurements of the building.

The conflict identification program 108 then identifies the roofs and generates a roof truss assembly comprised of members to provide for the required frame to create the model.

In step 404, the conflict identification program 108 identifies the roof truss members and analyzes the internal properties of the roof truss members. Once the conflict identification program 108 has identified the roof trusses, the conflict identification program 108 is able to identify the roof truss member individually so that the conflict identification program 108 is able to extract the necessary information related to each roof truss member. In some embodiments, the conflict identification program 108 identifies the position of the roof truss members relative to each other. For example, to make sure all horizontal members are substantially parallel and that the horizontal members are substantially perpendicular to the vertical members. For roof trusses the roof truss members are substantially parallel or perpendicular unlike with roof trusses and roof trusses.

The conflict identification program 108 determines the actual values for the roof truss member properties. These properties are related to all features of the roof truss member; length, height, width, thickness of material, orientation, position, cutouts, apertures, lips, flanges, Swedge, and the like. For example, the roof truss members position relative to the x, y, and z axes. In some embodiments, the limitation of the shipping vehicles sets a maximum length of the roof truss members. In some embodiments, the limitations of the manufacturing machines are used to set the required values. For example, the thickness of the material is a limitation on the roof truss members.

In decision 406, the conflict identification program 108 determines if the roof truss member's have any internal conflicts (e.g. if the actual values of the member properties are within the range of the required values). The measured actual values are compared to the required values. This comparison assists in confirming that the roof truss members are of the proper dimensions and have the features in the proper locations so that when the roof truss is assembled the members line up, the features of the members are in the proper location, and the roof truss is assembled correctly. If the conflict identification program 108 determines that an actual value of any properties of the roof truss member are outside the predetermined tolerance range of the property, the conflict identification program 108 creates the sick list and adds the identified member to the sick list.

In step 408, the conflict identification program 108 creates the sick list of the roof truss members which have issues. This list may be the identification of the members within the model as highlighted or identified from the other members. In some embodiments, the sick list is a list showing the actual values, the required values, and the differences between these two values (delta) and highlight the member data to alert a user.

In step 410, the conflict identification program 108 modifies the conflicting roof truss members. Through either an automated process or the selection of a user, the conflict identification program 108 is able to modify the conflicting roof truss members to fall within the tolerance range set for each property value which is conflicting. In some embodiments, this may require performing additional modifications to the roof truss member if the modification results in other features of the roof truss member becoming problematic and conflicting with the required values. For example, if a roof truss member is shortened and thus moving the position of an aperture, the aperture position may be adjusted to accommodate the shortening of the roof truss member.

In step 412, the conflict identification program 108 analyzes the roof truss members relative to the assembled roof truss. The conflict identification program 108 analyzes the roof truss members interaction with one another. This may include members are overlapping, incorrect placement of fastening positions, incorrect member direction or orientation at connections, incorrect gaps or spacing between roof trusses uneven height or width, are a few examples of potential internal conflicts. For example, the conflict identification program 108 may analyze the actual values of the orientation, position, length, width, and overlapping area of the top chord 902, the bottom chord 908, the end members 904, the center member 910, and the set of web members 912, 918, 914, 920, and 916 relative to one another to determine if there is any problematic overlapping or conflicts between the members. The set of web members 912, 918, 914, 920, and 916 orientation, overlap with one another and the top and bottom chords and the like are all analysed to determine the actual values for the members interactions. The location of the dimples relative on each track, and the other actual measurements of the interaction of the members. The bottom chords 908 are analyzed based on their actual overlap, their actual position, and their actual orientation relative to one another and the other members which interact with them.

In decision 414, the conflict identification program 108 determines if any of the members have external conflicts. The conflicts are based on the interaction between members of the roof truss. Based on the known requirements for the ideal interaction and a calculated value for the actual interaction between the members the conflict identification program 108 is able to determine if a conflict exists. If a conflict does exist the conflict identification program 108 creates a sick list of the external conflicts. If a conflict does not exist, the conflict identification program 108 completes the analysis.

In Step 416, the conflict identification program 108 analyzes the roof truss assemblies relative to the other roof truss assemblies and roof structure elements which the roof truss interacts with. This can be, that the assembly is of improper measurements, material, features, insufficient gap between two roof trusses or the like which would make the member have an internal conflict and not be possible to be created. If the member has negative or unrealistic values. The program analyzes vertical interface between each of the roof trusses for various features. Such as the required overlapping of each cold formed steel truss in horizontal and vertical plane is determined as per the location of junctions of truss and truss and gap required for proper connections of the assembly members. Actual overlapping of roof trusses and location of junctions of each roof truss assembly is determined from the actual position (coordinates) within the model.

In some embodiments, the program 108 analyzes for the interface of each roof truss assembly to determined the relationship between the trusses based on the global coordinates or position. The trusses should have sufficient gap (tolerance) in the horizontal direction while connecting with the trusses for proper connection. Actual gap (tolerance) between two overlapping trusses is determined based on the coordinates of the truss members.

In some embodiments, the program 108 analyzes for the interface of each roof truss assembly to determined the relationship between the trusses based on the global coordinates or position. The trusses should have sufficient gap (tolerance) in the vertical direction while connecting with the trusses for proper connection. Actual gap (tolerance) between two overlapping trusses is determined based on the coordinates of the truss members.

Placing of the trusses over the truss below it and connecting interface between the two trusses in horizontal plane is determined from the coordinates of the interacting members of the trusses. Both trusses should not overlap, and should not have a gap outside of the required value.

For proper connections, connecting trusses should have sufficient bearing area. Bearing area means when a truss is positioned above another truss, the area of interface between them is called the bearing area. For connection using screws it should have sufficient edge distances. Thus, the required bearing area is calculated from the number of screws required for the connection. Actual bearing area is obtained from locations of screws and their numbers used for connections by coordinates of the truss members within the model.

In decision 418, the conflict identification program 108 determines if any of the trusses have conflicts with other trusses. The conflicts are based on the interaction between the truss members of the interacting trusses. Based on the known requirements for the ideal interaction and a calculated value for the actual interaction between the members the conflict identification program 108 is able to determine if a conflict exists. The required minimum tolerance of each truss is determined as per the standard construction tolerances. The actual tolerance of each cold formed steel roof truss is determined from the model. If the required minimum tolerance and actual tolerance are same, then there is no conflict and if the required tolerance and actual tolerance are not same, then there is conflict. If a conflict does exist the conflict identification program 108 creates a sick list of the external conflicts. If a conflict does not exist, the conflict identification program 108 completes the analysis.

FIGS. 5, 6, and 7 depict various architectural illustration of a structure, in accordance with one embodiment of the present invention. The conflict identification program 108 may be provided these types of illustrations and analyses them to determine which features of the structure are the roof trusses. This determination is based on the position of the elements, the identified shape of the elements, the members (and orientation of the members) of the elements, and the like which would distinguish the roof trusses from the other elements of the building. In FIG. 5 , the roof 502 is clearly shown on the top of the building. In FIG. 6 , the roof 602 is clearing shown along with the overhang over the front and rear of the building. In FIG. 7 a dotted line 702 showing the outside edge of the roof is shown. This includes both internal and external roof trusses. Through the analysis of the building design, the conflict identification program 108 is able to establish a set of limits and requirements which the roof trusses and the roof truss members must adhere to. These illustrations depicted the floor plans to show walls, doors, stairs, windows, rooms, and other architectural features of each floor of the building. Based on the conflict identification program's 108 review of these drawings, the program is able to detect the overall dimensions of the roof trusses to assist in setting forth the required values and properties to which the roof truss members are analyzed.

FIG. 8 depicts a model 800 of a frame of a structure, in accordance with one embodiment of the present invention. This model provides all of the framing members including the walls, floors, and roofs. The conflict identification program 108 is able to take either the illustrations or model(s) and perform the analysis identified in FIG. 4 , as the program is able to detect which elements are the roof trusses (and members). In the depicted embodiment, the model depicts the structural framing members, with all the connection points for the frame members determined. This model would be analyzed for each structural wall member to determine any conflicts. If a conflict is found, that member may be highlighted or identified in a different color to allow easy visual identifies for the user to locate the conflict member.

FIGS. 9 and 10 depicts a model 900 of a roof truss system showing the connection in a horizontal plane, in accordance with one embodiment of the present invention. The depicted illustration shows a horizontal interface between a main truss 902 and a set of secondary trusses 904. The gap between the main truss 902 and the secondary truss 904 has a maximum and minimum distance which is acceptable for the actual measurements.

FIGS. 11 and 12 depicts a model 1100 of a roof truss system showing the connection in a vertical interface, in accordance with one embodiment of the present invention. The depicted illustration shows a main truss 1102 and a secondary truss 1104 through a vertical upper interface connection. The gap between the main truss 1102 and the secondary truss 1104 has a maximum and minimum distance which is acceptable for the actual measurements.

FIG. 13 depicts a model 1300 of a roof truss system showing the connection in a vertical interface, in accordance with one embodiment of the present invention. The depicted illustration shows and upper vertical handshake connection between a main truss 1302 and a dormer truss 1304. There is a required minimum tolerance between the first side 1303 and the second side 1305 of the dormer truss 1304.

This is an analysis relative to the horizontal interface between trusses, the vertical upper handshake and the vertical lower handshake. The horizontal interface is shown in FIGS. 9 and 10 , where a secondary truss 902 is secured to a main truss 904. The measurements have a tolerance of a maximum and minimum which the distances can be between to not be conflicting.

The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, fire joists, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

Present invention: should not be taken as an absolute indication that the subject matter described by the term “present invention” is covered by either the claims as they are filed, or by the claims that may eventually issue after patent prosecution; while the term “present invention” is used to help the reader to get a general feel for which disclosures herein that are believed as maybe being new, this understanding, as indicated by use of the term “present invention,” is tentative and provisional and subject to change over the course of patent prosecution as relevant information is developed and as the claims are potentially amended.

The foregoing descriptions of various embodiments have been presented only for purposes of illustration and description. They are not intended to be exhaustive or to limit the present invention to the forms disclosed. Accordingly, many modifications and variations of the present invention are possible in light of the above teachings will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the present invention. In the specification and claims the term “comprising” shall be understood to have a broad meaning similar to the term “including” and will be understood to imply the inclusion of a stated integer or step or group of integers or steps but not the exclusion of any other integer or step or group of integers or steps. This definition also applies to variations on the term “comprising” such as “comprise” and “comprises”.

Although various representative embodiments of this invention have been described above with a certain degree of particularity, those skilled in the art could make numerous alterations to the disclosed embodiments without departing from the spirit or scope of the inventive subject matter set forth in the specification and claims. Joinder references (e.g. attached, adhered, joined) are to be construed broadly and may include intermediate members between a connection of elements and relative movement between elements. As such, joinder references do not necessarily infer that two elements are directly connected and in fixed relation to each other. Moreover, network connection references are to be construed broadly and may include intermediate members or devices between network connections of elements. As such, network connection references do not necessarily infer that two elements are in direct communication with each other. In some instances, in methodologies directly or indirectly set forth herein, various steps and operations are described in one possible order of operation, but those skilled in the art will recognize that steps and operations may be rearranged, replaced or eliminated without necessarily departing from the spirit and scope of the present invention. It is intended that all matter contained in the above description or shown in the accompanying drawings shall be interpreted as illustrative only and not limiting. Changes in detail or structure may be made without departing from the spirit of the invention as defined in the appended claims.

Although the present invention has been described with reference to the embodiments outlined above, various alternatives, modifications, variations, improvements and/or substantial equivalents, whether known or that are or may be presently foreseen, may become apparent to those having at least ordinary skill in the art. Listing the steps of a method in a certain order does not constitute any limitation on the order of the steps of the method. Accordingly, the embodiments of the invention set forth above are intended to be illustrative, not limiting. Persons skilled in the art will recognize that changes may be made in form and detail without departing from the spirit and scope of the invention. Therefore, the invention is intended to embrace all known or earlier developed alternatives, modifications, variations, improvements and/or substantial equivalents. 

What is claimed is:
 1. A computer-implemented method comprising: receiving, by one or more processors, a model of a building associated with required regulations, the model comprises of a plurality of assemblies, and each assembly comprise of a plurality of members; identifying, by one or more processors, a set of assemblies related to roof trusses within the model based on characteristics associated with roof truss assemblies; analyzing, by the one or more processors, interaction between at least two roof truss assemblies in horizontal and vertical interfaces and interaction between one roof truss assembly and a non-structural assembly; detecting, by the one or more processors, an inter-assembly conflicts; wherein the inter-assembly conflicts include members are overlapping, incorrect placement of fastening positions, incorrect member direction or orientation at connections, incorrect gaps between roof trusses and uneven height or width of member; recording, by the one or more processors, a set of requirements associated with the interface type; identifying, by the one or more processors, each of the members of the roof truss assemblies involved in the inter-assembly conflict as conflicting members, wherein each the identified conflicting members are marked in the model; generating, by the one or more processors, a sick list of the members involved in the inter-assembly conflict and does not meet the set of requirements; highlighting the sick list of the members in different color for easy visual identification to alert user; determining, by the one or more processors, one or more modifications automatically to correct the sick list; and implementing the one or more modifications automatically into the model to conform the required regulations.
 2. The computer-implemented method of claim 1, further comprising, marking, by the one or more processors, the members involved in the at least one of member-to-member conflict, assembly-to-assembly conflict and mating conflicts, wherein the conflicting members are distinguished from non-conflicting members.
 3. The computer-implemented method of claim 1, further comprising, integrating, by the one or more processors, a sub-system into the model, wherein the sub system interfaces with at least one roof truss assembly.
 4. The computer implemented method of claim 3, further comprising, analyzing, by the one or more processors, the plurality of members which interact with the installation of the sub-system, and determining if at least one of the plurality of member conflicts with the sub-system.
 5. The computer-implemented method of claim 4, further comprising, modifying, by the one or more processors, the at least one of the plurality of members which conflict with the sub-system.
 6. A computer program product, the computer program product comprising a non-transitory computer readable storage medium having program instructions embodied therewith, the program instructions executable to cause the computing device to: receive a model of a building associated with required regulations, wherein the model comprise a plurality of roof truss assemblies and each roof truss assembly comprise a plurality of members; identify a set of assemblies related to roof trusses within the model based on characteristics associated with roof truss assemblies; analyze interaction between at least two roof truss assemblies in horizontal and vertical interfaces and interaction between one roof truss assembly and a non-structural assembly; detect an inter-assembly conflicts; wherein the inter-assembly conflicts include members are overlapping, incorrect placement of fastening positions, incorrect member direction or orientation at connections, incorrect gaps between roof trusses and uneven height or width of member; record a set of requirements associated with the interface type; identify each of the members of the roof truss assemblies involved in the inter-assembly conflict as conflicting members, wherein each the identified conflicting members are marked in the model; generate a sick list of the members involved in the inter-assembly conflict and does not meet the set of requirements; highlighting the sick list of the members in different color for easy visual identification to alert user; determine one or more modifications automatically to correct the sick list and implement the one or more modifications automatically into the model to conform the required regulations.
 7. The computer program product of claim 6, further comprising, analyze an interface between at least two assemblies, wherein one of the assemblies is a roof truss assembly.
 8. The computer program product of claim 6, further comprising, analyze the model and at least one sub-system, wherein each sub-system has a set of components and determining if a member of a roof truss assembly conflict with any of the components of the sub-system.
 9. The computer program product of claim 6, further comprising, assessing an interface between the sets of assemblies, wherein it is determined if any assemblies conflict with a roof truss assembly, and if a conflict is discovered identifying the members of the assemblies which are conflicting.
 10. The computer program product of claim 9, further comprising, determining if the members of the conflicting assemblies are to be adjusted or if the assembly is to be adjusted, and adjusting the members or the assembly.
 11. A system comprising: a CPU, a computer readable memory and a non-transitory computer readable storage medium associated with a computing device; program instructions to identify a plurality of members and a plurality of roof truss assemblies of a model of a building associated with required regulations wherein each roof truss assembly comprise of a set of members; program instructions to identify roof truss assemblies based on a specific set of characteristics associated with the roof truss assemblies program instructions to analyze interaction between at least two roof truss assemblies in horizontal and vertical interfaces and interaction between one roof truss assembly and a non-structural assembly; program instructions to detect an inter-assembly conflicts; wherein the inter-assembly conflicts include members are overlapping, incorrect placement of fastening positions, incorrect member direction or orientation at connections, incorrect gaps between roof trusses and uneven height or width of member; program instructions to record a set of requirements associated with the interface type; program instructions to identify each of the members of the roof truss assemblies involved in the inter-assembly conflict as conflicting members, wherein each the identified conflicting members are marked in the model; program instructions to generate a sick list of the members involved in the inter-assembly conflict and does not meet the set of requirements; program instructions to highlight the sick list of the members in different color for easy visual identification to alert user; program instructions to determine one or more modifications automatically to correct the sick list; program instructions to implement the one or more modifications automatically into the model to conform the required regulations; and program instructions to generate a report of the of conflicting members and the types of conflicts which resolved.
 12. The system of claim 11, further comprising, program instructions to Incorporate sub-systems into the model and analyzing the members to determine if they conflict with the sub-system.
 13. The system of claim 11, further comprising, program instructions to identify, roof truss assemblies within the model, wherein the roof truss assemblies are comprised of at least two members.
 14. The system of claim 11, further comprising, program instructions to identify, roof truss assemblies within the model, wherein the roof truss assemblies are comprised of at least two members.
 15. The system of claim 11, wherein the horizontal interfacing roof truss members are parallel or perpendicular depending on vertical members.
 16. The system of claim 11, wherein the horizontal interfacing roof truss assemblies are not substantially parallel. 